home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
clipper
/
nfsrc21.zip
/
NANFOR.RMK
< prev
next >
Wrap
Text File
|
1992-10-20
|
21KB
|
574 lines
/*
* File......: NANFOR.RMK
* Date......: $Date: 20 Oct 1992 01:18:38 $
* Revision..: $Revision: 1.16 $
* Log file..: $Logfile: C:/nanfor/src/nanfor.rmv $
*
* Modification history:
* ---------------------
*
* $Log: C:/nanfor/src/nanfor.rmv $
*
* Rev 1.16 20 Oct 1992 01:18:38 GLENN
* Adjusted librarian's path macros.
*
* Rev 1.15 16 Oct 1992 00:18:42 GLENN
* Deleted ATPROMPT.PRG.
*
* Rev 1.14 16 Oct 1992 00:11:16 GLENN
* Added DBFHANDL.ASM, DBTHANDL.ASM, DISPCNT.ASM, NTXHANDL.ASM, and
* SETKEYS.ASM. Removed TMENU.ASM.
*
* Rev 1.13 13 Oct 1992 20:41:38 GLENN
* Remove TMENU.*; Ted is revamping his @ prompt/menu to replacement.
*
* Rev 1.12 03 Oct 1992 02:15:02 GLENN
* Deleted ORIGIN.ASM and replaced with ORIGIN.C.
*
* Rev 1.11 03 Oct 1992 02:09:18 GLENN
* Got rid of reference to fttext.h; Steve Larsen's new mods don't
* require it.
*
* Rev 1.10 29 Sep 1992 00:42:14 GLENN
* Added support for explicit pointers to include files; and documented
* it. Reset the "rebuilding environment" to a directory structure not
* so deeply nested.
*
* Rev 1.9 28 Sep 1992 23:18:02 GLENN
* Updated the documentation to reflect the current status of the
* CompuServe forum. Removed test driver support (this wouldn't have
* ever worked anyway). Reset the default variables for the librarian's
* environment, as is his sacred right.
*
* Rev 1.8 22 Aug 1992 16:51:04 GLENN
* Added PVID.PRG.
*
* Rev 1.7 01 Jul 1992 02:20:20 GLENN
* Added SLEEP.PRG.
*
* Rev 1.6 01 Jul 1992 01:24:10 GLENN
* Added SETLASTK.ASM.
*
* Rev 1.5 16 Aug 1991 00:02:38 GLENN
* MADD.PRG and MONTH.PRG dependency lines were written incorrectly
* so these objects were being built whether they changed or not.
* Fixed.
*
* Rev 1.4 15 Aug 1991 23:09:02 GLENN
* Forest Belt proofread/edited/cleaned up doc
*
* Rev 1.3 17 Jul 1991 22:50:50 GLENN
* Added a couple last minute sources
*
* Rev 1.2 14 Jun 1991 20:28:30 GLENN
* Moved SHADOW.OBJ from MASM section to TASM section
*
* Rev 1.1 14 Jun 1991 19:58:38 GLENN
* Removed NOVCONS.OBJ pending some bug fixes.
*
* Rev 1.0 14 Jun 1991 18:46:46 GLENN
* Initial revision.
*
*/
/* ----------------------------------------------------------------------
The Nanforum Toolkit Master Makefile READ THIS BEFORE USING!!!
----------------------------------------------------------------------
This makefile will allow you to use RMAKE, provided with every
Clipper 5.01 package, to maintain your own copy of the Nanforum
Toolkit. It is also an example of one way to use RMAKE on a
large project. This is the exact copy used by the Nanforum Toolkit
librarian.
To use it, you must first understand what it does, and what your
limitations are. A discussion of MAKE utlities is beyond the scope
of this comment; read the Clipper documentation, or the Norton Guide
file, for more information on RMAKE.
*** Compilers and Assemblers you need
Note that currently, Nanforum Toolkit sources are written in
Assembly language, Clipper, and C. Within the realm of assembly
language, our contributors have submitted code that is designed
for Borland's Turbo Assembler (TASM) and Microsoft's Macro Assembler
(MASM). So, right now, in order to do a perfect re-build of
the Nanforum Toolkit, you must have these tools:
Microsoft C (v5.1 or later)
Microsoft Macro Assembler (v 5.1 or later)
Borland Turbo Assembler
Nantucket Clipper v5.01 or later
If you know much about assembly language, you can convert MASM
sources to TASM and vice versa, but that is up to you.
*** Library Utility
In addition, you must have a library utility. Microsoft supplies
LIB.EXE with its Compiler products, for example. LIB will work
fine with this makefile. Note that we assume a command line syntax
for library utilities that works like this:
lib <libname> -+objname
Note the "-+" directive, indicating "replace module." If your
library utility does not support this syntax on the command line,
then you will have to edit the relevant lines in the makefile.
A version of LIB.EXE can be found on CompuServe. Download S12776.ARC
from the MSL forum.
*** Assumptions about your environment
NANFOR.RMK makes just a few assumptions about your environment:
Assumption What to change if we're wrong
---------- -----------------------------
Microsoft C is being Look for the .C source inference
used rule below, and change it to *your*
compiler, making sure your switches
are correct. Note that some source
may not compile without MSC, so edits
may be required. Try to use MSC.
This is also where you will change the
makefile to whatever *you* call your
C compiler (CL for Microsoft C 5.1.)
Microsoft Assembler Look for all occurences of MASM in
executable is called this makefile and change them to
MASM.EXE whatever *you* call MASM.
Borland's Turbo Assembler Look for all occurences of TASM in
executable is called this makefile and change them to
TASM.EXE whatever *you* call TASM.
Clipper compiler executable Look for the .PRG source inference
is called CLIPPER.EXE rule below, and change it to whatever
*you* call Clipper.
*** Customizing the Makefile
We have tried not to assume anything about your environment except
what is described above. To achieve that flexibility, you must
check and set some macros that can be found just below this
documentation. They are:
l Path to the resulting library (i.e., \nanfor)
o Path to where .obj files should be put (i.e., \nanfor\obj)
s Path to where the source code is found (i.e., \nanfor\src)
c5 Path and name of Clipper 5.0 compiler
c5g Clipper 5 option line for include files (see below)
ma Path to Microsoft Macro Assembler .EXE
ta Path to Turbo Assembler .EXE
mc Path to Microsoft C 5.1
mcg Microsoft C option line for include files (see below)
ml Path and name of library utility (i.e., \bin\lib)
Note that directory paths should *not* end in a backslash.
If you like to keep your .obj and source files in the same
directory, simply point the paths to the same place.
Be careful not to nest your "rebuilding environment" (see below)
to deep; you could end up creating very long command lines that
will exceed DOS limits.
*** How include files are handled
The librarian maintains a few versions of Clipper on his disk
at any one time, as well as one or two versions of various
C compilers. As time went on, he realized that the SET
INCLUDE= and SET LIB= environment variables were somewhat evil.
For example, toolkit v2.1 is supposed to be built with the
exact includes supplied by Computer Associates for 5.01a, but the
librarian's INCLUDE envar points to the 5.0 includes. Resetting
these variables is easy but if one forgets, there is a potential
for version confusion.
To eliminate confusion over where the globals are, the following
was decided:
All include files shall be pointed to explicitly using
compiler command line options, and if possible, the